home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Collection of Tools & Utilities
/
Collection of Tools and Utilities.iso
/
graphic
/
pbmpl91d.zip
/
PBMPLUS
/
README
< prev
next >
Wrap
Text File
|
1993-01-08
|
16KB
|
409 lines
This is the README file for DJ's GCC port to DOS ("djgpp")
Contents:
* Overview
* What's available
* How to install
* Deviations and Caveats
* Copyright information
Disclaimer: This software is distributed WITHOUT ANY WARRANTY; without
even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR
PURPOSE.
DJ Delorie
USmail: 24 Kirsten Ave, Rochester, NH 03867-2954, USA
email: dj@ctron.com
mailing list: djgpp@sun.soe.clarkson.edu (listserv@sun.soe.clarkson.edu)
Overview:
This package contains a 32-bit 80386 DOS extender with symbolic
debugger, a C/C++ compiler with utilities, development libraries, and
source code. It generates full 32-bit programs and supports full
virtual memory with paging to disk.
Requirements:
A 80386-based IBM compatible PC or PS/2, approximately 4-5Mb of hard
drive space, and 512K RAM. Available extended (or expanded under VCPI)
memory is strongly recommended.
Supported Wares:
* Up to 128M of extended memory (expanded under VCPI)
* Up to 128M of disk space used for swapping
* SuperVGA 256-color mode up to 1024x768
* 80387
* XMS & VDISK memory allocation strategies
* VCPI programs, such as QEMM, DESQview, and 386MAX
Unsupported:
* DPMI
* Microsoft Windows
* Multiprocessing (fork())
File location:
host: barnacle.erc.clarkson.edu
login: ftp
password: send your e-mail address
directory: ~ftp/pub/msdos/djgpp
Many thanks to the sysops at Clarkson for providing a home to djgpp!
As a convenience to non-FTP users, djgpp is also stored on Clarkson's
archive server. To access the archive server, do this:
% mail archive-server@barnacle.erc.clarkson.edu
Subject: <none>
help
index msdos/djgpp
^D
NOTE: In accordance with FSF CopyLeft, you are not allowed to upload
this program to a distribution site unless that site also makes the FSF
sources for these programs available. Please read the file COPYING for
more details. FSF sources are available on prep.ai.mit.edu, and on
barnacle.erc.clarkson.edu
NOTE: If your application links in object modules that were written
by FSF, your application counts as a "derived work" and must obey
the provisions of the FSF Copyrights. See the file COPYING for
details. Specifically, the C++ classes in libc.a and obstacks are
FSF works that are covered by the GNU GPL. The mere act of compiling
does not affect the copyright status of your program.
INSTALLING:
To install, you must do the following:
* Create a "temp" directory, like c:\tmp.
* Create a directory to install in, like c:\djgpp.
* Un-zip the appropriate zipfiles in the install directory.
C:\DJGPP> pkunzip -d -o djdev109.zip
C:\DJGPP> pkunzip -d -o djgas138.zip
C:\DJGPP> pkunzip -d -o djgcc222.zip
* Add the following lines to C:\CONFIG.SYS file (or edit existing
files= and shell= lines as appropriate). The files= line prevents "too many
open files" errors when compiling, and the shell= line prevents "Out of
environment space" errors when setting lots of environment variables.
files=15
shell=c:\command.com c:\ /e:600 /p
The values 15 and 600 are close to minimal. You may want to increase them
to provide a little more margin.
* Add the following lines to C:\AUTOEXEC.BAT:
set COMPILER_PATH=c:/djgpp/bin
set C_INCLUDE_PATH=c:/djgpp/include
set CPLUS_INCLUDE_PATH=c:/djgpp/cplusinc;c:/djgpp/include
^^^ only needed if you are compiling c++ programs
set OBJC_INCLUDE_PATH=c:/djgpp/include
^^^ only needed if you are compiling objective-C programs
set OBJCPLUS_INCLUDE_PATH=c:/djgpp/include
^^^ only needed if you are compiling objective-C++ programs
set LIBRARY_PATH=c:/djgpp/lib
set TMPDIR=c:/tmp
^^^ this is where gcc's temp files go
set GO32TMP=c:/tmp
^^^ this is where your paging file goes - if not set, the
variables TMP and TEMP are checked in that order
set GO32=ansi driver c:/djgpp/drivers/SOMETHING.grd gw 1024 gh 768
^^^ whatever driver works with your VGA (optional)
set BISON_SIMPLE=c:/djgpp/lib/bison.simple
^^^ only needed if you use bison
set BISON_HAIRY=c:/djgpp/lib/bison.hairy
^^^ only needed if you use bison
set FLEX_SKELETON=c:/djgpp/lib/flex.skeleton
^^^ only needed if you use flex
Remember that unless you manually type these at the command line,
they won't take effect until you reboot. Don't include the "ansi"
keyword in the "go32" variable if you don't have an ANSI.SYS driver
or equivalent.
* Add your binaries directory to your PATH in C:\AUTOEXEC.BAT
SET PATH= . . . ;C:\DJGPP\BIN
That's it! djgpp is now installed on your system.
The GO32 environment variable:
This variable controls the options available in go32 or debug32. The
syntax of this variable is:
SET GO32=[parm [value]] [parm [value]] . . .
Parameters:
ansi Use ANSI commands to control the color in debug32
mono Use the Monochrome monitor for debugging - useful when
debugging graphics applications
1rm Redirect stdout (file #1) to the monochrome monitor
2rm Redirect stderr (file #2) to the monochrome monitor
1r2 Redirect stdout (file #1) to stderr (file #2)
2r1 Redirect stderr (file #2) to stdout (file #1)
glob enable globbing (default)
noglob disable globbing
emu [path] Use the specified file as the 80387 emulator
driver [path] Use the specified file as the graphics driver
gw [width] Default graphics width
gh [height] Default graphics height
tw [width] Default text width
th [height] Default text height
nc [colors] Number of colors (for new-style drivers only - see cbgrx*.zip)
These parameters may occur in any order.
Note that "1rm" and "2rm" are done before "1r2" and "2r1", so "1rm 2r1" sends
stdout to the mono monitor and stderr to any redirection used.
Examples:
C:\> set GO32=mono driver c:\djgpp\drivers\tseng4k.grd gw 1024 gh 768 tw 132 th 43 nc 256
C:\> set GO32=ansi
C:\> set GO32=driver c:\djgpp\drivers\tseng4k.grd ansi
C:\> set GO32=mono 1rm 2rm
Deviations and Caveats:
GCC/G++ deviates from the U**x version in a number of ways, mostly to
accomodate deficiencies in the MS-DOS environment, and my own laziness.
* An 80387 is required to do floating point. An emulator is provided.
cc1 and cc1plus shouldn't use the 387 unless compiling floating point
code. The environment variable "387" can override the auto-detection
routine:
SET 387=YES to force 387 handlers to be enabled
SET 387=NO to force 387 accesses to fault
SET 387=QUERY to get a message showing the results of the auto-detection
If no 80387 is present and the program attempts to use it, a message
indicating where the instruction is will be displayed. To use the
387 emulator, add "emu c:\djgpp\emu387\emu387" to the GO32 environment
variable. Specifying use of the emulator overrides the "387"
environment variable and autodetection code.
* The VDISK method of allocating extended memory is supported. The
INT 15h method is also. When the extender runs out of conventional and
extended memory, it uses a paging file named $(GO32TMP)/pgXXXXXX.386, where
XXXX is an unspecified hex value. This file is normally removed on exit.
* Up to 128 MB of physical memory and 128 MB of disk swap space are allowed.
A 512K machine is sufficient, but very slow due to paging.
* The utilies support the MS-DOS standard response file method for giving
more than 128 bytes of command line. Example: "gcc -o foo @foo.lnk" where
foo.lnk contains a list of .o files. Wildcard expansion (globbing) is
performed on the parameters, unless they are surrounded by single quotes.
Double quotes can be used to prevent spaces from separating